Configure Outgoing Filtering with Exchange Online (Microsoft 365)

Before beginning, edit your SPF record to include the SpamExperts servers.

You must complete all steps below for correct operation of the outbound filtering.

In order to configure outgoing filtering for Exchange Online/Microsoft 365 follow these steps:

  1. Step 1: Create Outgoing User/Authentication Method in SpamExperts
  2. Step 2: Create the connector in Exchange Online
  3. Step 3: Create the Transport Rule in Exchange Online

Step 1: Create Outgoing User/Authentication Method in SpamExperts

  1. Log in to the SpamExperts control panel as an admin
  2. Select General > Domains Overview then click on the relevant domain to open the Domain Level Control Panel
  3. Select Outgoing > Manage Users
  4. Select the Authenticating Domain tab and ensure that the domain you are using with Exchange Online is shown
  5. Enter a secure password and click Add and configure

    6. The secure password is only required to complete the configuration process. Once set, it is no longer needed.

  6. Configure the Authentication method as required, ensuring that Re-authentication permitted is enabled

    7. The Outgoing User Settings page is displayed:

    • Password - Create or change the password for the authenticating domain

      This password is unique to the Authenticating Domain user and is not tied to any other user credentials. This password can be anything you please.

    • Confirm Password - Confirm the password
    • Domain - This is the domain the IP address or IP range is associated to
    • Identification Method - Choose from: “envelope sender”, “authentication user” or “Header” as the identification method (See the Manage Identities page for more details)
      Envelope SenderUse this if your system enforces the “envelope sender” (or MAIL FROM value). This is typically used by SpamExperts users.
      Authentication UserThe outgoing user’s authentication details. This is the best choice when you are providing unique usernames and passwords for each outgoing user, rather than using a smarthost system.
      Header

      If you choose this option, you are able to add any number of identification headers that we should search for in the message. For example, you might have a system that adds an “X-Client-ID” header, which uniquely identifies each of your end users. For each header, you may choose to either use the entire header value as the identity, or you can provide a regular expression that extracts out a part of the value to use. You may also choose to have our software remove the header after we have found the identity, if you don’t want this to be available to the recipient of the message.

      We strongly recommend that an identity Header is set for all outgoing traffic. This makes monitoring and taking action against spammers much easier.

    • Automatic lock - When enabled, and when the system detects that the user has sent approx 5 spam messages in 10 minutes, the user will be locked automatically. The user cannot send mail until they are unlocked (the administrator can do this from the alert sent or from the Outgoing Users/Authentication Methods page)

      We recommend that you do not enable the Automatic lock if you are using IP authentication within a smarthost.

    • Lock Identities Automatically - This spam prevention, when enabled and the system detects that the identity has sent approx 5 spam messages in 10 minutes, the identity will be locked automatically. The identity cannot send mail until they have been unlocked. The identity can be unlocked from the Manage Identities page
    • User and Identity Lock timeout - The amount of time an outgoing user or identity will be unable to send messages. This only applies to if you are using the Automatic User Lock or the Automatic Identity Lock
    • Maximum unlocks by timeout - The maximum number of times the user will be automatically unlocked after the time-out value has passed. After this has been depleted, the user will have to be manually unlocked
    • Lock Template - Select the email template to be used to inform the user of the lock
    • Enable outgoing connection limits - Enable or disable limits on outgoing connections whether spam or not, to prevent bulk mailing

      Only enable limits when preventing unusual volume of SMTP connections for the following time frames:

      • Limit per month - The amount of outgoing connections that can be opened per month
      • Limit per week - The amount of outgoing connections that can be opened per week
      • Limit per day - The amount of outgoing connections that can be opened per day
      • Limit per hour - The amount of outgoing connections that can be opened per hour
      • Limit per minute - The amount of outgoing connections that can be opened per minute
    • Valid Sender Address Required - (Available at Super-Admin Level only) When enabled, the filtering servers do a 'null sender' callout to verify the sender. This means that the filtering server will connect to the sending address mailserver, using a sender of "<>" (as a bounce message does), and the specified sender as the RCPT To. After checking the sender, the connection will be properly closed (i.e. no message is actually sent). This is a good way to stop spammers and we recommend having this option enabled
    • DKIM Selector- Choose the selector you wish to use at domain level. Use the default or add one that has been generated using the DKIM Certificate Generation tool. Once you have created the certificate you need to add the TXT to your DNS

      For Example, if you generate a key for selector mailassure1, publish the DKIM Key under the DNS Record mailassure1._domainkey.example.invalid. Then enter mailassure1 in this DKIM Selector field on SpamExperts.

    • Maximum number of recipients per day - The maximum number of SMTP recipients the authenticating method can send emails to in a 24 hour period
    • Quarantine Response – When an outgoing message is detected as spam and it goes into the outgoing quarantine, the response you send back to the sending server can be Rejected or Accepted
      • If 'Rejected' (550), legitimate senders will receive a bounce message when their mail gets blocked and quarantined even though the message is stored in the quarantine
      • If 'Accepted' (250), the SMTP response would be ‘Accept’ and the message would still be blocked and shown in the quarantine but the sender will not receive a bounce message and will not know that the message is in the outgoing quarantine

      The administrator will be notified that there are messages in the outgoing quarantine with an Abuse Report (ARF) if the Administrator’s contact email address has been added into the Outgoing > Settings page in the Domain Level Control Panel (see Configure the Abuse Report Address). Alternatively, use the Email Scout Reports to create a schedule report with details of outgoing quarantine content.

    • Message archiving for senders - Enabled/Disabled – If enabled, submission messages will be added to the archiving account of the envelope sender's domain. See Enable Archiving for Outgoing Mail.
    • Block attachments with macros for senders - If enabled, any message with a document based attachment that contains any kind of macro will be rejected
    • Block potentially unwanted attachments - If enabled, any messages with an attachment that is considered dangerous or otherwise unwanted will be rejected

      This restriction applies to Outbound messages only, to apply this restriction for Inbound mail, see Manage Attachment Restrictions.

    • Reject messages from newly registered domains - (if available) If set, then any message sent from a domain that is newly registered (less than a day) will be rejected
    • Re-authenticate permitted - If enabled, authorized servers will be able to relay email on behalf of this user
  7. Click Save

For full details on Authentication methods, see Outgoing Users/Authentication Methods

Step 2: Create the connector in Exchange Online

Microsoft has specific instructions on setting up a third party cloud spam filtering system. For detailed instructions on configuring a Microsoft 365 environment, see the Microsoft documentation for this here. A summary of one possible configuration is below.

  1. Log in to the Microsoft 365 Admin Center
  2. In the navigation menu, select Show all

  3. Click Exchange to open the Exchange Admin Center

  4. Open Mail flow > Connectors

  5. Click + Add a connector
    1. Set the connection from: Office 365
    2. Set the connection to: partner organization
  6. Click Next
  7. Give the connector a name (for example: SpamExperts Outbound filter) and click Next
  8. On the Use of Connector window, select Only when I have a transport rule set up that redirects messages to this connector and click Next
  9. Select Route email through these smarthosts and enter:
    2. smtp.antispamcloud.com
  10. Click +, then click Next
  11. On the Security Restrictions tab, ensure Always use Transport Layer Security (TLS) to secure the connection (recommended) is ticked
    1. Use Issued by a trusted certificate authority (CA)
    2. Click Next
  12. Enter any valid email address in the Validation email field
  13. Click +, then Validate

    If this validation fails after completing all of the instructions in Step 1 and Step 2 successfully, you may skip this to complete connector creation and then proceed to Step 3.

  14. Once the email is validated, click Next
  15. Review the details for the connector and click Create connector

Step 3: Create the Transport Rule in Exchange Online

The below instructions are just an example, please specify your settings for your unique transport rule needs.

  1. Log in to the Microsoft 365 Admin Center
  2. Using the left hand menu, navigate to New Exchange Admin Center (this is default)
  3. Open Mail flow > Rules
  4. Create a new Rule by selecting the +
  5. Click More options at the bottom of the window
  6. Give the rule a name (for example: Route through SpamExperts, or SpamExperts Outbound)
  7. Fill the fields in as follows:
    1. Apply this rule if: The sender's domain is domain.invalid

      Where domain.invalid is replaced with the domain(s) required

      Specify the domain(s) in the pop-up, ensuring you click the + icon to add each one

    2. Do the following: Redirect messages to the following connector

      Select the connector made in step 2 from the dropdown provided in the Select Connector pop-up

    3. Except if: The recipient is internal/external

      Select inside the organization from the Select Recipient Location pop-up

    4. Chose a mode for this rule: Enforce
  8. Click Save

Once this is done, any traffic matching your outgoing sender domain will be relayed via the transport rule and be processed by the filtering servers.

For additional details on configuring this in either the Classic EAC or the New EAC, see the Microsoft documentation to set up connectors for secure mail flow.